Dialog Flow Management In Hierarchical Task Dialogs

ABSTRACT

Methods and systems for managing multiple tasks using a dialog are presented. In some embodiments, a processor may parse a first natural language user input received at a user device to extract task related information from the first natural language user input. In response to identifying that the first natural language user input comprises a request to perform a first task, the processor may initiate execution of the first task. The user device may receive a second natural language user input after execution of the first task has been initiated which requests execution of a second task. The processor may initiate execution of the second task before execution of the first task is complete.

FIELD

The present disclosure relates to computerized natural languageprocessing applications, and more specifically, to coordinatingexecution of multiple dialog-based tasks in conversational dialogapplications.

BACKGROUND

With advances in natural language processing (NLP), there is anincreasing demand to integrate speech recognition capabilities withinteractive software applications such that the user can perform simpletasks using voice commands that were previously performed by customerservice representatives or by the user interacting with an interactivegraphical user interface of a computerized system. Automating some ofthese customer representative tasks can reduce customer representativehours and operating expenses. This automation is only effective if theusers find a friendly and easy to use environment.

As an example, software agents in the form of intelligent personalassistants are being integrated into the operating systems of mobiledevices and automobile dashboards. However, such speech recognitionsoftware is able to parse a very limited number of voice commands.Although the user can input voice commands for a handful of commandssuch as searching the worldwide web, taking a photograph, or composing amessage, such intelligent personal assistants do not offer a mechanismfor managing an entire set of tasks implemented by a more complexapplication.

Several mobile and web applications are task oriented. Certain dialogsystems employing NLP and natural language understanding (NLU) supportexecuting of discrete tasks such as filling forms, completing an onlinepurchase, checking a user's bank balance information, etc. However,these systems cannot engage in dialog with the user and simultaneouslyperform a series of unrelated and related tasks that the user instructswhile conversing with the dialog system.

SUMMARY

The following presents a simplified summary of various aspects describedherein. This summary is not an extensive overview, and is not intendedto identify key or critical elements or to delineate the scope of theclaims. The following summary merely presents some concepts in asimplified form as an introductory prelude to the more detaileddescription provided below.

Various aspects of the disclosure provide efficient, effective,functional, and convenient ways of executing dialog based tasks. Inparticular, in one or more embodiments discussed in greater detailbelow, dialog based task functionalities are implemented, and/or used ina number of different ways to provide one or more of these and/or otheradvantages.

In some embodiments, a computing device may identify that a firstnatural language user input comprises a request to perform a firstdialog task. In response identifying a request to perform a first dialogtask, the computing device may initiate execution of a first pluralityof task agents comprised by the first dialog task according to a firsthierarchical order by which task agents in the first plurality ofsubtasks are arranged for execution. In response to determining that asecond natural language user input, received at the computing deviceduring execution of the first dialog task, comprises a request toperform a second dialog task, the computing device may determine thatthe second dialog task is to be executed before execution of the firstdialog task is completed. The computing device may initiate execution ofa second plurality of task agents comprised by the second dialog task,prior to completion of the first dialog task, in an order based on asecond hierarchical order by which task agents in the second pluralityof task agents are scheduled for execution.

In some embodiments, in response to the second natural language userinput requesting execution of a second dialog task, the computing devicemay suspend execution the first dialog task. The computing device maypreserve a state of a natural language dialog and user inputs receivedduring execution of the first dialog task. In response to determiningthat execution of the second dialog task has completed, the computingdevice may retrieve the state of the natural language dialog and userinputs received during execution of the first dialog task. The computingdevice may resume execution of the first dialog task from a point atwhich the first dialog task was suspended.

In some embodiments, at least one task agent of the first plurality oftask agents may engage a user in a natural language dialog to extractinformation, from the second natural language user input received duringexecution of the first dialog task, required for the execution of thefirst dialog task.

In some embodiments, execution of the first plurality of task agents mayfurther comprise scheduling each task agent of the first plurality oftask agents for execution in an order based on the first hierarchicalorder of arrangement of the first plurality of task agents. Execution ofthe second plurality of task agents may comprise scheduling each taskagent of the second plurality of task agents for execution in an orderbased on the second hierarchical order of arrangement of the secondplurality of task agents.

In some embodiments, the computing device may determine whetherexecution of the second dialog task should be prevented.

In some embodiments, the computing device may identify which dialog taskis to be executed based on the second natural language user input andinformation in the first plurality of task agents.

In some embodiments, the first dialog task and the second dialog taskare managed simultaneously. The computing device switch betweendifferent dialog tasks based on a natural language dialog between theuser and the computing device.

In some embodiments, the computing device may generate a list ofparameters that each of the first plurality of task agents expects toidentify from the natural language dialog. In response to parsing thenatural language dialog, the computing device may associate at least oneuser input value from the natural language dialog with each parameter inthe list of parameters and may execute the first plurality of taskagents using the user input value.

In some embodiments, the computing device may determine that the secondnatural language user input comprises instructions to modify thecurrently executing first dialog task by adding additional task agentsto the first hierarchical order. The computing device may scheduleexecution of the additional task agents to the first dialog taskcurrently being executed according to the first hierarchical order.

These and additional aspects will be appreciated with the benefit of thedisclosures discussed in further detail below.

BRIEF DESCRIPTION OF THE DRAWINGS

A more complete understanding of the present disclosure and theadvantages thereof may be acquired by referring to the followingdescription in consideration of the accompanying drawings, in which likereference numbers indicate like features, and wherein:

FIG. 1 depicts an illustrative computer system architecture that may beused in accordance with one or more illustrative aspects describedherein.

FIG. 2 depicts an illustrative multi-modal conversational dialogapplication arrangement that shares context information betweencomponents in accordance with one or more illustrative aspects describedherein.

FIG. 3 depicts an illustrative conversational dialog applicationarrangement in which a task manager communicates with the tasks of thedialog application in accordance with one or more illustrative aspectsdescribed herein.

FIG. 4 depicts an illustrative tree diagram architecture of a taskimplemented by the dialog application in accordance with one or moreillustrative aspects described herein.

FIG. 5A depicts an illustrative diagram of the task tree of a conferenceroom reservation task in accordance with one or more illustrativeaspects described herein.

FIG. 5B depicts an illustrative diagram of a task dialog engine thatexecutes a conversation dialog between a user to execute a conferenceroom reservation task in accordance with one or more illustrativeaspects described herein.

FIG. 6 depicts an illustrative diagram of a task manager incommunication with multiple tasks in accordance with one or moreillustrative aspects described herein.

FIG. 7 depicts a flowchart that illustrates a method of coordinatingexecution of multiple dialog tasks in accordance with one or moreillustrative aspects described herein.

FIGS. 8A and 8B depict a flowchart that illustrates a method ofexecuting a dialog task in accordance with one or more illustrativeaspects described herein.

DETAILED DESCRIPTION

In traditional conversational dialog applications, speech input isprocessed to facilitate execution of a task. Tasks such as ordering apizza using an automated food ordering application or paying a billthrough an online banking application may be performed in conjunctionwith dialog applications. The dialog application typically performs atask in isolation by gathering required information from a user througha series of preset prompts. The conversations initiated by such dialogapplications are very rigid and perform only a single task in isolation.Dialog applications cannot handle user commands for multiple taskssimultaneously and cannot handle managing multiple tasks simultaneously.Conventional dialog applications limit the dialog for a particular taskand do not allow invoking a separate task from the dialog of a currentlyexecuting task. In accordance with aspects of the disclosure, aconversational dialog arrangement is provided, which allows the varioussystem components to manage an entire set of tasks associated with anapplication while processing speech input in a conversational dialogwith the user to perform multiple tasks in parallel.

A task manager may be used to manage a variety of tasks that anapplication may implement. A task utilizing dialog management may bemodeled as an ordered tree of dialog agents and agencies. Each dialogagent or dialog agency may be an independent subroutine which performs aspecific function required by the task. By segmenting a task intohierarchically decomposed dialog agents and agencies and controlling theorder in which each dialog agent and agency is invoked in performing agiven task, a conversational dialog application may manage the executionof multiple different tasks. The conversational dialog application maycreate separate execution contexts for each task that it manages,allowing multiple tasks of the same or a different application to be runsimultaneously in parallel.

In some embodiments, at runtime, the dialog application may choose torun a particular task based on user input (e.g., speech commands, usertext commands, user manipulation of elements displayed in an interactiveuser interface, etc.) or the state of the application. Once launched,the task may consume dialog concurrently with other forms of user input.At any future time, the application may choose to invoke a second taskregardless of whether the current task being performed has completed.When the task is switched in such a manner, the application may suspendthe current task being performed and may preserve any input collectedfor the current task and activate the second task. The previous taskthat was suspended may be automatically resumed when the active secondtask terminates or when the application resumes the previous task as aresult of user input or application logic. In some embodiments, anapplication may launch and manage multiple instances of the same task.

As an example embodiment, a task manager may implement a mobile bankingapplication. Once the application launches, the user may instruct theapplication to “pay his bill.” Accordingly, the task manager may capturethis speech command and as a result, launch a new bill paying task inthe mobile banking application and may display a pay bill screen on theuser interface with which a user can interact. The user may answerprompts such as specifying his account information but in the middle ofthe bill paying task, the user may realize that he needs to transfermoney into his bank's checking account in order to pay the bill and say“transfer money” or another similar phrase. The task manager may thensuspend the bill paying task while preserving the user responses offeredin the bill paying task and the current state of the bill paying taskand may launch a new money transfer task using the mobile bankingapplication. After completion of the voice enabled transfer of fundsinto the checking account with the money transfer task, the task managermay revert to the suspended state of the bill paying task and resume thebill paying task without having to prompt the user for information forthe bill paying task that the user has previously inputted.

The task manager may enable such seamless switching of tasks by managingeach task's subroutines and function calls. The task manager may manageall tasks supported by a particular application within a single dialogby reducing programming complexity, computing operations, and additionalcommunications between an application and a remote server that resultfrom multiple tasks being implemented without a task managercoordinating each task's subroutines.

In the following description of the various embodiments, reference ismade to the accompanying drawings, which form a part hereof, and inwhich is shown by way of illustration various embodiments. It is to beunderstood that other embodiments may be utilized and structural andfunctional modifications may be made without departing from the scope ofthe present disclosure. Aspects described herein are capable of otherembodiments and of being practiced or being carried out in various ways.Also, it is to be understood that the phraseology and terminology usedherein are for the purpose of description and should not be regarded aslimiting. Rather, the phrases and terms used herein are to be giventheir broadest interpretation and meaning. The use of “including” and“comprising” and variations thereof is meant to encompass the itemslisted thereafter and equivalents thereof as well as additional itemsand equivalents thereof. The use of the terms “mounted,” “connected,”“coupled,” “positioned,” “engaged” and similar terms, is meant toinclude both direct and indirect mounting, connecting, coupling,positioning and engaging.

FIG. 1 illustrates one example of a network architecture and dataprocessing device that may be used to implement one or more illustrativeaspects described herein. Various network nodes 103, 105, 107, and 109may be interconnected via a wide area network (WAN) 101, such as theInternet. Other networks may also or alternatively be used, includingprivate intranets, corporate networks, LANs, wireless networks, personalnetworks (PAN), and the like. Network 101 is for illustration purposesand may be replaced with fewer or additional computer networks. A localarea network (LAN) may have one or more of any known LAN topology andmay use one or more of a variety of different protocols, such asEthernet. Devices 103, 105, 107, 109 and other devices (not shown) maybe connected to one or more of the networks via twisted pair wires,coaxial cable, fiber optics, radio waves or other communication media.

The term “network” as used herein and depicted in the drawings refersnot only to systems in which remote storage devices are coupled togethervia one or more communication paths, but also to stand-alone devicesthat may be coupled, from time to time, to such systems that havestorage capability. Consequently, the term “network” includes not only a“physical network” but also a “content network,” which is comprised ofthe data—attributable to a single entity—which resides across allphysical networks.

The components may include data server 103, web server 105, and clientcomputers 107, 109. Data server 103 provides overall access, control andadministration of databases and control software for performing one ormore illustrative aspects as described herein. Data server 103 may beconnected to web server 105 through which users interact with and obtaindata as requested. Alternatively, data server 103 may act as a webserver itself and be directly connected to the Internet. Data server 103may be connected to web server 105 through the network 101 (e.g., theInternet), via direct or indirect connection, or via some other network.Users may interact with the data server 103 using remote computers 107,109, e.g., using a web browser to connect to the data server 103 via oneor more externally exposed web sites hosted by web server 105. Clientcomputers 107, 109 may be used in concert with data server 103 to accessdata stored therein, or may be used for other purposes. For example,from client device 107 a user may access web server 105 using anInternet browser, as is known in the art, or by executing a softwareapplication that communicates with web server 105 and/or data server 103over a computer network (such as the Internet).

Servers and applications may be combined on the same physical machines,and retain separate virtual or logical addresses, or may reside onseparate physical machines. FIG. 1 illustrates just one example of anetwork architecture that may be used, and those of skill in the artwill appreciate that the specific network architecture and dataprocessing devices used may vary, and are secondary to the functionalitythat they provide, as further described herein. For example, servicesprovided by web server 105 and data server 103 may be combined on asingle server.

Each component 103, 105, 107, 109 may be any type of known computer,server, or data processing device. Data server 103, e.g., may include aprocessor 111 controlling overall operation of the data server 103. Dataserver 103 may further include RAM 113, ROM 115, network interface 117,input/output interfaces 119 (e.g., keyboard, mouse, display, printer,etc.), and memory 121. I/O 119 may include a variety of interface unitsand drives for reading, writing, displaying, and/or printing data orfiles. Memory 121 may further store operating system software 123 forcontrolling overall operation of the data processing device 103, controllogic 125 for instructing data server 103 to perform aspects asdescribed herein, and other application software 127 providingsecondary, support, and/or other functionality which may or may not beused in conjunction with aspects of the present disclosure. The controllogic may also be referred to herein as the data server software 125.Functionality of the data server software may refer to operations ordecisions made automatically based on rules coded into the controllogic, made manually by a user providing input into the system, and/or acombination of automatic processing based on user input (e.g., queries,data updates, etc.).

Memory 121 may also store data used in performance of one or moreaspects of the disclosure, including a first database 129 and a seconddatabase 131. In some embodiments, the first database may include thesecond database (e.g., as a separate table, report, etc.). That is, theinformation can be stored in a single database, or separated intodifferent logical, virtual, or physical databases, depending on systemdesign. Devices 105, 107, 109 may have similar or different architectureas described with respect to device 103. Those of skill in the art willappreciate that the functionality of data processing device 103 (ordevice 105, 107, 109) as described herein may be spread across multipledata processing devices, for example, to distribute processing loadacross multiple computers, to segregate transactions based on geographiclocation, user access level, quality of service (QoS), etc.

FIG. 2 depicts an example multi-modal conversational dialog applicationarrangement that shares context information between components inaccordance with one or more example embodiments. A user client 201 maydeliver output prompts to a human user and may receive natural languagedialog inputs, including speech inputs, from the human user. Anautomatic speech recognition (ASR) engine 202 may process the speechinputs to determine corresponding sequences of representative textwords. A natural language understanding (NLU) engine 203 may process thetext words to determine corresponding semantic interpretations. A dialogmanager (DM) 204 may generate the output prompts and respond to thesemantic interpretations so as to manage a dialog process with the humanuser. Context sharing module 205 may provide a common context sharingmechanism so that each of the dialog components—user client 201, ASRengine 202, NLU engine 203, and dialog manager 204—may share contextinformation with each other so that the operation of each dialogcomponent reflects available context information.

The context sharing module 205 may manage dialog context information ofthe dialog manager 204 based on maintaining a dialog belief state thatrepresents the collective knowledge accumulated from the user inputthroughout the dialog. An expectation agenda may represent what newpieces of information the dialog manager 204 still expects to collect atany given point in the dialog process. The dialog focus may representwhat specific information the dialog manager 204 just explicitlyrequested from the user, and similarly the dialog manager 204 may alsotrack the currently selected items, which typically may be candidatevalues among which the user needs to choose for disambiguation, forselecting a given specific option (one itinerary, one reservation hour,etc.), and for choosing one of multiple possible next actions (“booknow”, “modify reservation”, “cancel”, etc.).

Based on such an approach, a dialog context protocol may be defined, forexample, as:

-   -   BELIEF=list of pairs of concepts (key, values) collected        throughout the dialog where the key is a name that identifies a        specific kind of concept and the values are the corresponding        concept values. For example “I want to book a meeting on May        first” would yield a BELIEF={(DATE, “2012/05/01”),        (INTENTION=“new_meeting”)}.    -   FOCUS=the concept key. For example, following a question of the        system “What time would you like the meeting at?”, the focus may        be START_TIME.    -   EXPECTATION=list of concept keys the system may expect to        receive. For instance, in the example above, while FOCUS is        START_TIME, EXPECTATION may contain DURATION, END_TIME,        PARTICIPANTS, LOCATION, . . . .    -   SELECTED_ITEMS: a list of key-value pairs of currently selected        concept candidates among which the user needs to pick. Thus a        dialog prompt: “do you mean Debbie Sanders or Debbie Xanders?”        would yield to SELECTED_ITEMS {(CONTACT, Debbie Sanders),        (CONTACT, Debbie Xanders)}.

Communicating this dialog context information back to the NLU engine 203may enable the NLU engine 203 to weight focus and expectation conceptsmore heavily. And communicating such dialog context information back tothe ASR engine 202 may allow for smart dynamic optimization of therecognition vocabulary, and communicating the dialog context informationback to the user client 201 may help determine part of the currentvisual display on that device.

Similarly, the context sharing module 205 may also manage visual/clientcontext information of the user client 201. One specific example ofvisual context would be when the user looks at a specific day of hercalendar application on the visual display of the user client 201 andsays: “Book a meeting at 1 pm,” she probably means to book it for thedate currently in view in the calendar application.

The user client 201 may also communicate touch input information via thecontext sharing module 205 to the dialog manager 204 by sending thesemantic interpretations corresponding to the equivalent naturallanguage command. For instance, clicking on a link to “Book now” maytranslate into INTENTION:confirmBooking. In addition, the user client201 may send contextual information by prefixing each such semantickey-value input pairs by the keyword CONTEXT. In that case, the dialogmanager 204 may treat this information as “contextual” and may considerit for default values, but not as explicit user input.

In some embodiments, ASR engine 202 may process the speech inputs ofusers to text strings using speech to text conversion algorithms. ASRengine 202 may constantly pay attention to user feedback to betterunderstand the user's accent, speech patterns, and pronunciationpatterns to convert the user speech input into text with a high degreeof accuracy. For example, ASR engine 202 may monitor any user correctionof specific converted words and input the user correction as feedback toadjust the speech to text conversion algorithm to better learn theuser's particular pronunciation of certain words.

In some embodiments, user client 201 may also be configured to receivenon-speech inputs from the user such as text strings inputted by a userusing a keyboard, touchscreen, joystick, or another form of user inputdevice at user client 201. The user may also respond to output promptspresented by selecting from touchscreen options presented by user client201. The user input to such prompts may be processed by dialog manager204, context sharing module 205, and NLU engine 203 in a similar manneras speech inputs received at user client 201.

Dialog manager 204 may continuously be monitoring for any speech inputfrom a user client, independent of tasks implemented at the dialogmanager. For example, dialog manager 204 accepts voice commands from auser even when any tasks currently being implemented do not require auser input. A task manager, implemented by the dialog manager 204, mayprocess the voice command and in response to the voice command, launch anew task or modify the execution of one or more tasks currently beingimplemented.

Task manager 302 may be in communication with tasks 310, 320, and 330 ofa dialog application 300, as shown in FIG. 3. Each task may berepresented by a two tier architecture comprising a dialog taskspecification and a dialog engine. A human's task may be modeled byseparating task specific behavior and more general dialog behavior(i.e., conversational strategies). A description of the task to beperformed may be provided by segmenting the task into a hierarchicallydecomposed set of subroutines in the task specification. The mechanismsfor maintaining coherence and continuity of a conversation are generatedby a dialog engine.

In the embodiment shown in FIG. 3, dialog task specification layers 314,324, and 334 may comprise all of the dialog logic that tasks 310, 320,and 330 are governed by, respectively. Dialog engines 312, 322, and 322may control the dialog implemented by tasks 310, 320, and 330,respectively, in an application 300 by executing tasks according to thelogic instructed in their corresponding dialog task specification layers314, 324, and 334, respectively. Task manager 302 may control theexecution of each task in application 300 by passing instructions to thedialog engines of such tasks. In response to voice commands, taskmanager 302 may instruct different task dialog engines to either start,pause or abort operation. Task manager 302 may also coordinate theexecution of tasks 310, 320, and 330 by pausing execution of one task infavor of another task or by facilitating inter-process communication(IPC) between different tasks implemented by the dialog application oreven across multiple different dialog applications.

Task manager 302 may also control specific instances of a task bypassing values to a task dialog engine that it is in communication withand retrieving specific values and parameters set during the executionof a particular task. Task manager 302 may be configured to executefunction calls to initiate particular dialog agents and agencies out ofthe order specified in the task specification of a particular task. Taskmanager 302 may be configured to retrieve user supplied information fromdialog agents and agencies for use in a different task to minimizeprompting the user for information that the user has previously enteredwith relation to a previously run task. Accordingly, task manager 302may be configured to set values for different concepts managed byparticular dialog agents or dialog agencies of any one of the tasks itmanages. Task manager 302 may be able to monitor the state of each taskand determine which tasks are currently active and how long ago certaintasks were last active. Task manager 302 may use such activityinformation to schedule execution of tasks. Task manager 302 may alsoprocess user commands and schedule an order of execution of tasksaccording to the dialog input. Task manager 302 may be configured toschedule an initial task by default upon start of the dialogapplication.

Dialog engines 312, 322, and 322 may contribute conversationalstrategies such as turn taking between the application 300 and the userby controlling the execution time of each task subroutine found in thecorresponding task specification layer. Dialog engines may also have theability to suspend and resume each task. Dialog engines may be able torepeat a particular task subroutine, perform subroutines out of order,execute loops, and manipulate subroutines as desired to perform thetask. Dialog engines may be controlled by task manager 302 to controlexecution of a task in a customized manner. Dialog engines may be ableto respond to a user call for help and provide assistance. For example,in response to a task manager command to provide help to the user, adialog engine may initiate a subroutine that provides helpfulinformation or assistance to the user responsive to a help request.

In some embodiments, dialog engines may be responsible for maintainingthe sophistication of a conversation dialog by implementingconversational strategies to the dialog between the application and theuser according to human conversational techniques. For example, humanscollaborate to establish a common ground in conversations. The dialogengine, while implementing the subroutines for a task specified in thetask specification, may use probabilistic modeling and decision theoryto make grounding decisions. By monitoring the amount of discrepancythere exists in the dialog between the user responses to the applicationprompts, the dialog engine may be able to determine whether the dialogneeds to be adjusted to maintain the conversation. If such adetermination is made, then the dialog engine may implement additionalsubroutines from the task specification to guide the conversation suchthat the system achieves a higher confidence level that the discrepancybetween the application and the user in the subject matter of theconversation is minimized. Dialog engines for each task may monitor agrounding state (e.g., computed using Bayesian algorithms) of aconversation and adjust the conversation by adding or modifyingapplication prompts to the user such that the necessary informationrequired to complete the task is received from the user in an efficientmanner.

Task specifications 312, 314, and 316 describing task specific behaviormay be modeled with tree diagrams of task subcomponents. Most goaloriented dialog tasks have an identifiable structure which lends itselfto a hierarchical description. The subcomponents may be typicallyindependent, leading to ease in design and maintenance and providescalability to each task for insertion of additional steps andrepetition of steps at run time, allowing for dynamic construction ofdialog structure. Dialog task specifications 314, 324, and 334 maycomprise dialog agents and dialog agencies, which may each beindependent program subroutines and are described in greater detailbelow with relation to FIGS. 4 and 5. Dialog agents may also be referredto herein as task agents or task dialog agents. Dialog agencies may alsobe referred to herein as task agencies or task dialog agencies. Thestructures of task specifications are described in greater detail belowwith connection to FIGS. 4 and 5A.

Dialog engines 312, 322, and 332 may control the dialog between the userand the application during implementation of their respective tasks.Dialog engines 312, 322, and 332 may execute the dialog taskspecifications for their corresponding tasks in two phases: an executionphase and an input phase. During the execution phase, various dialogagents (i.e., task subroutines) may be executed to produce the dialogapplication's behavior. During the input phase, the dialog applicationmay collect and incorporate information from the user's input. Theexecution and input phases are described in greater detail below withconnection to FIG. 5B.

In some embodiments, the task manager 302 may invoke different tasksthat it manages based on the user dialog. For example, the task manager302 may manage multiple tasks 3110, 320, and 330 by communicating withtheir respective dialog engines 312, 322, and 332. In oneimplementation, a single task may be executed at a given time but thetask manager 302 may manage multiple tasks simultaneously even thoughonly one of the tasks is actively executing at any given time. Forexample, the task manager 302 may manage each of the different tasksthat it manages in different execution spaces (e.g., different memoryareas of a device's memory such as memory 121). Dialog engines 312, 322,and 332 may identify when a user desires, from received dialog input, toswitch to a second task while a first task is in progress. Dialogengines 312, 322, and 332 may communicate with task manager 302 that thedialog is requesting a task different from their own. Accordingly, thetask manager 302 may suspend the first task and activate a second task.For example, the task manager 302 may instruct dialog engine 312 tosuspend task 310 in favor task 320. Task manager 302 may then instructdialog engine 322 to execute task 320. The task manager 302 may switchbetween multiple tasks that they manage based on the nature of thedialog. The task manager 302 may also queue a plurality of tasks in agiven order and execute a second task once the task preceding it in thequeue is completed.

In some embodiments, the application 300 may be able to override anytasks that have been invoked by the task manager 302 or dialog engines312, 322, and 332. The application 300 may have control over any tasks,or any tasks' dialog agents and dialog agencies. For example, once taskmanager 302 has instructed dialog engine 312 to activate task 310 at agiven time, application 300 may determine that task 310 should not beactivated at the given time. Accordingly, application 300 may suspendexecution task 310. Application 300 may override task requests passedfrom task manager 302 to dialog engines 312, 322, and 332 in order toprevent the execution of tasks which, if run at a given time, may causeinstability in certain application processes, cause application 300 tofault or crash, or cause any runtime errors.

FIG. 4 depicts a tree diagram 400 of a task implemented by the dialogapplication. In particular, tree diagram 400 illustrates an illustrativeorganizational structure for the task specification of a dialogapplication task. Root node 402 may be the topmost node in the taskspecification layer. The root node may control the execution of childrennodes 410, 412, and 414 that are both connected to the root node in thetask tree diagram 400 of the application. Each node of the task tree 400may be a dialog agency or a dialog agent. Terminating nodes 414, 420,422, 430, and 432 of task tree 400 may be dialog agents andnon-terminating nodes 410, 412, and 424 may be dialog agencies.

In some embodiments, each dialog agent in a task tree handles a portionof the dialog task. A dialog agent may comprise an independentsubroutine, software module, or function call that includes instructionsto perform a specific task function. There may be four fundamental typesof dialog agents: 1) an inform dialog agent such as inform dialog agent420; 2) a request dialog agent such request dialog agent 422; 3) anexpect dialog agent such as expect dialog agents 430 and 432; and 4) adomain operation dialog agent such domain operation dialog agent 414.Inform dialog agents may transmit an output to the user, either in theform of synthesized speech output or a visual output on a display deviceof a client device. Inform dialog agents may present the user withinformation or acknowledge a user's input according to conversationalstrategies to maintain a continuous dialog between the application andthe user. A request dialog agent may request information from the user.For example, a request dialog agent may prompt the user for informationand listen for user speech input in response to the prompt.Alternatively, the request dialog agent may also allow the user toanswer a prompt by typing an answer or by selecting from one of severaloptions displayed on a user interface display. An expect dialog agentmay include instructions that allow the application task to expectinformation to be inputted from the user without prompting the user forany information. Domain operation dialog agents may include instructionsto perform a function that processes information received by the userbut does not involve user input or output.

Dialog agencies such as dialog agencies 410, 412, and 424 may controlexecution of their subsumed dialog agents. Dialog agencies may capturehigh level temporal and logical structure of a particular task andcontrol when and how the dialog agents which they control should beexecuted. Each dialog agent may subsume multiple different dialogagents. Dialog agents may be controlled by dialog agencies, root node402 or even by a task manager.

Each dialog agent and dialog agency may include instructions toimplement an execution routine in which the function that they encode isperformed. The execute routine for a dialog agent may be specific to thefundamental type of the dialog agent (i.e., inform, request, expect, ordomain operation). For example, inform type dialog agents may generatean output when their execution routine is implemented while request typedialog agents may initiate an input phase to collect a user's input to aprompt. Each dialog agent may also comprise a set of preconditions andtriggers that must be met before their respective execution routines maybe implemented. For example, a request dialog agent 422 that requeststhe user to specify which bill to pay will initiate its executionroutine after the request dialog agent is specified with preconditioninformation encoded in the request dialog agent. For example, onceinformation that identifies the user and a request to pay a bill havebeen received, the request dialog agent may be executed.

Execution routines of dialog agencies may specify the order in whicheach dialog agency's subsumed dialog agents may be executed. Dialogagencies may select from a set of different execution policies for theirsubsumed agents and agencies (hereinafter referred to as subsumed dialogagents or subsumed dialog agencies). As an example, a dialog agency withmultiple subsumed dialog agents may execute the dialog agents in a leftto right order of arrangement on task tree 400 of the dialog agents'placement. A dialog agency may also plan execution of its subsumeddialog agents in a sophisticated manner by determining if a particulardialog agent's execution provides much needed system resources andscheduling execution of such identified dialog agents. A task managermay also control the order of execution of a particular dialog agency'ssubsumed dialog agents. For example, a task manger may determine that acertain dialog agent yields necessary information that can be passed toa different dialog application task that the task manager is alsomanaging. Accordingly, the task manager may instruct a dialog agency toreorder the order in which the identified dialog agent is executed withrespect to other subsumed dialog agents if such a reordering of theorder of execution of subsumed dialog agents does not interfere with theefficient operation of the task. The task manager may reorder the orderof execution of certain dialog agents with respect to the orderspecified in a task specification by suspending and resuming the dialogagents and agencies. For example, the task specification for a giventask may specify, in task tree 400, that dialog agent 430 is to beexecuted before dialog agent 432. However, the task manager may chooseto modify the order of execution such that dialog agent 432 is executedbefore dialog agent 430. Accordingly, after the dialog engine executesdialog agency 424 and initiates execution dialog agent 430 as specifiedby task tree 400, the task manager may instruct the dialog engine tosuspend dialog agent 430 and initiate execution of dialog agent 432.Once dialog agent 432 has been executed, the task manager may instructthe dialog engine to resume execution of dialog agent 430. In thismanner, by suspending and resuming certain dialog agents and agencies,the task manager may reorder the execution order of dialog agents andagencies in a manner that it best determines suits the needs of receiveddialog inputs.

In some embodiments, a dialog agency may also modify the order ofexecution of its subsumed dialog agents. The dialog agency maycontinuously modify the order of execution of its subsumed dialog agentsas the dialog agency or task manger learns, through reinforcementlearning methods and other Markov decision-making processes, how tobetter perform a dialog task. For example, the task manager, root node,or dialog agency may decide that in order to better perform a particulartask, an additional function (i.e., dialog agent) may need to be addedto a task. The exact position in which the new dialog agent may beinserted (i.e., under which dialog agency) in the task specification maybe determined. The identified dialog agency under which the new dialogagent is to be added may reorder the order of execution of its subsumeddialog agents and/or agencies by evaluating the preconditions, triggers,and completion criteria of all of its previously subsumed dialog agentsand/or agencies and newly added dialog agents and/or agencies.

Dialog agencies and dialog agents may also each comprise completioncriteria that determine when each of their execution may be terminated.For example, a request dialog agent may terminate only when all the userresponses specified in the request dialog agent's completion criteriaare collected. Similarly, dialog agencies may also specify completioncriteria that must be met as a result of execution of their subsumeddialog agents and agencies in order to terminate successfully. Once suchcompletion criteria are met, the corresponding dialog agents or agenciesmay send a completion message to their parent node indicating completionof their assigned function such that the parent node may proceed tocontinue execution of another dialog agent or agency.

The dialog task specification may specify an overall hierarchical planfor the dialog task by associating preconditions, triggers, andcompletion criteria and may execute routines for each of the task 400'sdialog agents and dialog agencies. A dialog engine responsible fortraversing task tree 400 of a given task specification may specify theorder in which the dialog agents and/or agencies of task tree 400 are tobe executed with respect to each other by evaluating the policies (i.e.,preconditions, triggers, completion criteria etc.) of the dialog agentsand agencies of a task.

In some embodiments, dialog agents may store concepts and participate inthe input phase of a dialog engine to incorporate the informationcollected from a user into the dialog application system. For example, arequest dialog agent that prompts the user for identificationinformation may store such user identification information in the dialogapplication system for use by dialog agents of that particular task oreven a different task in the dialog application. Such concepts may alsoinclude task related information. Concepts stored by the dialog agentmay be represented as probability distributions over a set of possiblevalues that allow for decision making and updating the dialogapplication's belief system under uncertain circumstances. User inputvalues received from a dialog may be bound to concepts by dialog engine550 to satisfy the completion criteria of dialog agents and agencies.

In some embodiments, dialog agencies and a task manager may coordinatewith each other to facilitate implementation of conversational strategyin the execution of the dialog application. Conversational strategiessuch as turn taking behaviors, managing timing and order in whichinformation is presented and asked from the user, grounding behaviorsuch as seeking confirmation or reducing ambiguity in the conversation,repeating the last uttered dialog, suspending and resuming the dialog,restarting the dialog, and re-establishing context of the conversationmay be implemented by coordination of dialog agents and agencies withthe root node and task manager.

Certain control dialog agencies such as dialog agencies 404 and 406 maybe specified in the task specification to suspend and resume aconversation. In some embodiments, when a dialog engine receives arequest to suspend or resume a dialog task, the dialog engine mayinstruct task manager or root node 402 to modify task tree 400 bychanging placement of dialog agencies 404 and 406 such that they areconnected to the dialog agent or dialog agency that is currently beingexecuted. Suspend dialog agency 404 may include instructions for adialog engine to preserve a global state of the dialog, belief states,any concepts and information received from the user, and initializedroutines in a portion of the user device's memory until the task manageror root node instructs the application to resume the task. Accordingly,resume dialog agency 406 may include instructions to retrieve dialogglobal states, belief states, any concepts and information received fromthe user, and initialized routines stored by suspend dialog agency 404and restore the suspended dialog agents and agencies to resume theiroperation in response to a resume dialog agency 406 being triggered bythe root node 402 or a task manager.

In some embodiments, individual dialog agencies and dialog agents maycontrol turn taking protocols. For example, each dialog agent may beconfigured to display or output information to the user one after theother when the user has finished entering user input and is awaiting forthe dialog application to act. Similar, each dialog agency may controloutputting information encoded in the dialog agency's subsumed dialogagents in an ordered fashion by specifying that information must bedelivered to the user piecemeal to avoid overwhelming the user withinformation and in order to maintain good conversational strategy.

The dialog engine may be configured to control any dialog agents in tasktree 402 to repeat the last action performed by that dialog agent. Eachdialog agent may include the necessary structure to repeat portions ofits subroutines to present the user with information or audio output ifthe user has requested to have the last uttered information by theapplication repeated or have the last performed application actionrepeated.

FIG. 5A illustrates an illustrative task tree 500 for a conference roomreservation and scheduling task. Root node 502, labeled RoomLine,manages dialog agencies 510, 514, and 504 and dialog tasks 512 and 516.

Dialog agency 510 may correspond to a user login subroutine thatinvolves identifying a user, user registration and logon, andintroducing the user to the dialog application. Login dialog agency 510may be further decomposed into Welcome dialog agent 520 responsible forwelcoming and introducing the user to the dialog application and thesystem, dialog agents 522 and 524 that handle identifying the user andverifying his authentication credentials, and dialog agent 526 thatpresents the authenticated user with a greeting. Welcome dialog agent520 and GreetUser dialog agent 526 may be inform type dialog agents thatonly output information to the user in the form of audio or visualdisplays on a user interface display device. Alternatively, GreetUserdialog agent 526 may be an expect type dialog agent that could bothdisplay information to the user and receive information from the userregarding what action the user would next like to perform once he islogged in without explicitly prompting the user. AskRegistered dialogagent 522 may be a requested type dialog agent that requests containsdialog information necessary to prompt the user to enter a yes or noresponse of whether he is a registered user. Dialog agent 524 may be arequest type dialog agent that prompts the user to enter his username ornickname (i.e., Registered Name) to be used to address the user inconversations with the dialog application. Alternatively, dialog agent524 may be an expect type dialog agent that identifies the user nameinformation from the entered user information without having toexplicitly prompt the user to enter his name. For example, dialog agent524 may be able to identify the user's nickname by searching a local orremote database of user information by using the supplied authenticationcredentials.

In some embodiments, dialog agency 514 may correspond to a series offunction calls to obtain user information from the user. For example,the GetQuery dialog agency 514 may comprise subsumed dialog agent 530that obtains the date and time for which the user wishes to reserve anew conference, dialog agent 532 that obtains the location of the userdesired conference room, and dialog agency 534 that obtains furtherproperties and characteristics of the desired conference room. Dialogagency 534 may subsume dialog agents 540, 542, and 544 which may obtaininformation from the user whether the user a networked connection to theInternet, a projector, and a whiteboard are required in the desiredconference room, respectively. While dialog agents 530 and 532 may berequest type dialog agents which obtain the necessary criteria toimplement a search for a conference room, dialog agents 540, 542, and544 may be expect type dialog agents. By having expect type dialogagents 540, 542, and 544 be responsible for obtaining additionalconference room characteristics from the user, the dialog applicationaffords the user the flexibility to be able to specify additional searchcriteria if he so desires without burdening the user to be required toenter such optional search criteria.

Dialog agent GetResults 512, a child of the root RoomLine agency 502,may include functions to execute a search for the conference room at aremote backend server with the details of the user request obtained bydialog agency 514 and its subsumed dialog agents. Dialog agent 516 maypresent the results of the conference room search obtained by dialogagent 512 to the user. Dialog agent DiscussResults 516 may containinstructions for handling additional conversational dialog between theuser and the dialog application for negotiating and selecting aconference room based on the results presented to the user to select theconference room best matching the user's specific needs. Dialog agentGetResults 512 may be a domain operation type dialog agent that does notinput or output information to or from a user. Accordingly, dialog agent512 may not contain instructions to interact in dialog with a user.Instead, dialog agent 512 may comprise instructions, which whenimplemented, cause a search to be executed for a conference room thatmatches search parameters for the conference room obtained from the userfrom dialog agency 514 and its subsumed dialog agents 530, 532, 540,542, and 544. Dialog agent 512 may include instructions to search aremote database of conference room information that associatesconference room with searchable attributes to identify conference roomsthat match the user specified parameters.

Dialog agencies 504 and 506 for suspending and resuming any subroutineof task tree 500 may correspond to dialog agencies 404 and 406 of FIG.4. When a dialog engine receives a request to suspend or resume a dialogtask from the task manager, the dialog engine may instruct task manageror root node 502 to modify task tree 500 by changing placement of dialogagencies 504 and 506 such that they are connected to the dialog agent ordialog agency that is currently being executed.

FIG. 5B depicts an illustrative diagram of a task dialog engine 550 thatexecutes a conversation dialog between a user to execute a conferenceroom reservation task in conjunction with task specification 500 of FIG.5A. A dialog engine may step through the task tree of its correspondingtask specification to execute the task according to instructionsprovided in each task subroutine, encoded by the dialog agents anddialog agencies of the task specification, during an execution phase. Inthe execution phase, dialog engine 550 may track the dialog structureand may schedule dialog agents and dialog agencies of task tree 500 in adialog stack 560. During an input phase, dialog engine 550 may collectinformation from the user, by engaging the user in a dialog, to pass onto the subroutines being implemented in dialog stack 560.

During the execution phase, dialog engine 550 may traverse task tree 500of a corresponding task specification and place dialog agencies anddialog agents for execution in dialog stack 560. Initially, the rootdialog agent 502 may be placed on the dialog stack 560. Dialog stack 560may capture the temporal and hierarchical structure of the currentdialog, as determined by dialog engine 550. As dialog engine 550progresses down the task tree 500, dialog engine 550 may place otherdialog agencies and dialog agents subsumed by root dialog agent 502 ontop of stack 560 for execution above dialog agent 502. Dialog engine 550may schedule dialog agencies and dialog agents for execution in anordered fashion on stack 560 and may execute the dialog agent or agencyon top of stack 560. When a dialog agency is executed, dialog engine 550may schedule a dialog agent subsumed by the dialog agency being executedon top of stack 560 for execution. Execution of dialog agents generatesthe responses and actions of a dialog application. Once a dialog agentor dialog agency has completed execution and met its completioncriteria, dialog engine 550 may remove the completed dialog agent oragency from stack 560.

In some embodiments, the user can also take initiative and shift thefocus of the conversation to another part of the dialog task tree 500.For example, the dialog engine 550 may allow for the order of executionof dialog agents and agencies to be controlled by user input as long assuch user initiated execution does not violate any policies,preconditions, or task logic specified in any dialog agents, agencies,or the dialog engine 550. The task manager may monitor user inputreceived at any time, even during the execution phase and control thetask execution. The task manager may coordinate a user initiatedmodified execution of the task along with dialog engine 500. Forexample, the task manager may modify the order in which dialog agentsand agencies are executing by suspending certain dialog agents andagencies in task tree 500 to reorder the order of execution of dialogagents and agencies. Additionally, the task manager may modify task tree500 by adding new dialog agents onto preexisting nodes of task tree 500and direct dialog engine 500 to execute the modified task tree bypushing the newly added dialog agents onto dialog stack 560 according tothe new order specified in modified task tree 500.

The dialog engine 550 may also be configured to execute suspend andresume dialog agencies 504 and 506 at any time when directed by a user.For instance, dialog engine 550 may detect a user input to suspend atask or dialog agents and/or agencies at any point of time during thetask's execution phase. In response to such detected user suspendcommand, dialog engine 550 may trigger dialog agency 504 and push dialogagency 504 on top of dialog stack 560, even on top of any currentlyexecuting dialog agents on top of dialog stack 560 and immediatelyexecute agency 504 to suspend execution of the dialog agent immediatelyunderneath suspend agency 504 on dialog stack 560.

In some embodiments, dialog engine 550 may modify the order in whichdialog agents and/or agencies are executed and may choose a differentorder than the order specified in the task specification. For example,the task specification may specify that dialog agents listed in tasktree 500 are to be executed in a left first top first manner. Accordingto task tree 500, for example, dialog agent 530, that sets the date andtime the conference room is to be reserved, is to be executed beforedialog agent 532, responsible for setting the location of the requestedconference room. However, if the dialog engine 550 receives dialog inputfrom the user specifying the location of the requested conference roombefore the date and time for the conference room request, then dialogengine 550 may initiate execution of dialog agent 532 before dialogagent 530 by placing dialog agent 532 onto the dialog stack 560 at ahigher position than dialog agent 530.

In some embodiments, dialog engine 550 may push new agencies modelingconversational strategies on dialog stack 560. For example, dialogengine 550 may push conversational strategy dialog agencies notassociated with a particular agency or agent according to task tree 500to implement improved conversational strategy. Dialog engine 550 maycontinuously adjust its conversational strategy by monitoring whichconversational techniques achieve the highest grounding and minimize thedegree of uncertainty in conversations. Once dialog engine 550identifies a particular conversation technique that results in betterconversational strategy than one implemented by other dialog agents,dialog engine 550 may push the dialog agency corresponding to theimproved conversational technique onto the dialog stack 560 duringexecution of other dialog agents to further augment the conversationquality provided during their execution. In such a manner, dialog stack560 may track the current structure of the dialog, and dialog engine 550may provide support for focus shifts and handling sub-dialogs, duringthe execution phase.

Dialog engine 550 may process user input received during an input phaseto direct execution of dialog agents and agencies intelligently ondialog stack 560. An input phase of dialog engine 550's operation mayinvolve three stages: 1) construction of an expectation agenda 570,binding values received from user input to concepts and 3) analyzingneeds for focus shift in the dialog. Dialog engine 550 may implementeach of these three stages of the input phase sequentially or inparallel. In some implementations, dialog engine 550 may perform each ofthese three stages iteratively, using the output of any of the stages asfeedback inputs for another stage. For instance, dialog engine 550 maycontinuously modify expectation agenda 570 having bound user inputvalues to concepts or having analyzed needs for dialog focus shifts inorder to continuously improve the expectations of any dialog agents oragencies using the bounded concepts or dialog focus shifts.

In some embodiments, dialog engine 550 may construct expectation agenda570 for its corresponding task by collecting the expectations of eachdialog agent listed in task tree 500. For example, dialog engine 550 maytraverse task tree 570 in a top down manner starting with root node 502and instruct each dialog agent and dialog agency to declare itsexpectations. A dialog agent's expectation comprised in expectationagenda 570 may describe the semantic grammar slots that each agentmonitors, the concept that each dialog agent updates, and how such anupdate is performed. A dialog agency's expectations may comprise all ofthe expectations of its subsumed dialog agents. The example embodimentdepicted in FIG. 5B shows that expectation agenda 570 includesexpectations 572, 574, and 576 that correspond to the expectations ofdialog agencies 502, 510, and dialog agent 522, respectively. Sincedialog agency 502 subsumes dialog agency 510, which in turn subsumesdialog agent 522, expectation 572 of dialog agency 502, stored inexpectation agenda 570, includes expectations 572 and 576 as well asother expectations of different dialog agencies and dialog agents thatdialog agency 502 also subsumes. Since expectation agenda 570 maycomprise the expectations of each dialog agent and dialog agency in tasktree 500, expectation agenda 570 may include multiple sections includingexpectations 572, 574, and 576, the expectation sections may includeincreasingly larger contexts which are imposed by the current state ofthe dialog stack. In some embodiments, the expectation agenda may beconstructed by the dialog engine 550 during an input phase in which thedialog engine 550 may place the various dialog agencies and dialogagents of task tree 500 on dialog stack 560.

As shown in the example embodiment of FIG. 5B, expectation agenda 570may include expectations that specify information that each dialog agentexpects to receives upon execution. For example, AskRegistered dialogagent 522, which is responsible for verifying whether a user isregistered with the dialog application, may expect to receive a speechinput from user input in the form of a “yes” or “no” speech input.Expectation 576 also specifies that such an input may update theRegistered concept and that the Registered concept may be updated with abinary true or false binary result based on the received “yes” or “no”speech input. Similarly, Login dialog agency 510, which subsumesAskRegistered dialog agent 522 amongst other dialog agents and isresponsible for handling all user logon dialog agents, may expect toreceive a speech input from user input in the form of a “yes” or “no”speech input as the Registered concept and a user name from the userwhich updates the RegisteredName concept. Such expectations of dialogagency 510 may be stored as expectation 574 in expectation agenda 570.

In some embodiments, such as the embodiment depicted in FIG. 5B, dialogengine 550 may construct expectation agenda 570 in a piecemeal fashionin the order in which dialog agents and agencies are ordered in dialogstack 560. For example, dialog engine 550 may construct expectationagenda 570's data structure such that Login dialog agency 510'scorresponding expectation 574 is structured adjacent to expectation 576for dialog agent 522 that it subsumes. Similarly, dialog engine 550 mayconstruct expectation agenda 570's data structure such that expectation574 is structured adjacent to expectation 572, corresponding to dialogagency 502 that subsumes dialog agency 510 and is placed lower in dialogstack 560 than dialog agency 510. Such structuring of expectations inexpectation agenda 570 may be determined by dialog engine 550 to reflectthe order in which their corresponding dialog agents and dialog agenciesare placed in dialog stack 560.

In some embodiments, dialog engine 550 may match inputs received from auser with the declared expectations compiled in expectation agenda 570by a top down traversal of expectation 570. For example, dialog engine550 may match user inputs 580 received from a dialog between the system(i.e., the dialog application) and the user. In the example embodimentdepicted in FIG. 5B, the system outs system prompt 582 to the userasking whether the user is a registered user, as a result of theexecution of the AskRegistered dialog agent 522 placed on top of task560. Since dialog agent 522 is a request type dialog task, its executionrequires the system to wait for a user input after outputting a prompt.Accordingly, the dialog application waits until the user has respondedto prompt 582 with user input response 584. The dialog application mayparse the user response to generate parsed user input 586. The dialogapplication may generate parsed user input 586 by parsing user inputresponse 584 using NLP techniques. As shown in FIG. 5B, dialog engine550 may identify that the parsed user input 586 contains user inputvalues for the concepts that dialog agency 510 and dialog agent 522require. Accordingly, dialog engine 550 may bind such user input valuesfor whether the user is registered and user name to the Registered andRegisteredName concepts. Dialog engine 550 may determine that uponbinding user inputted values to concepts results in satisfying thecompletion criteria of dialog agent 522 and dialog agency 510, asoutlined by their respective expectations 576 and 574 in expectationagenda 570. Upon determining that the expectations of dialog agent 522and dialog agency 510 have been met, the dialog engine 550 may removedialog agent 522 and dialog agency 510 from dialog stack 560.

A top down traversal of expectation agenda 570, by dialog engine 550,may resolve any conflicts generated by multiple references to the sameconcept by different expectations. For example, if expectations existfor the same grammar slot in a dialog exist in multiple differentexpectations in expectation agenda 570, the expectation that is placedhigher on expectation agenda 570 may take precedence over theconflicting expectation placed lower in expectation agenda 570 since thehigher placed expectation is closer in context to the conversationbetween the dialog application and the user by virtue of being handledby the most subsumed dialog agent. Dialog engine 550 may structureexpectation agenda 570 and dialog stack 560 such that highest placeddialog agencies in task tree 500 (i.e., the task tree elements mostdistanced from the context of the actual conversation) are placed lowestin expectation agenda 570 and dialog stack 560. As an example, theembodiment depicted in FIG. 5B shows in expectation agenda 570 that the[yes] slot is bound to the Registered concept (setting its value totrue), but [user_name] is also bound to the Name concept which is alsoimplemented by AskName dialog agent 524 and referred to in itscorresponding expectation. Later when dialog engine 550 resumes theexecution phase, the AskName dialog agent 524 will already have itscompletion criterion satisfied (i.e. the Name concept will beavailable), and will therefore not be scheduled for execution.

During the input phase, dialog engine 550 may analyze user input 580 forfocus shifts in the dialog between the system and the user. Dialogengine 550 may determine if the focus of the conversation should beshifted in light of the recent input. The system may determine whetherany of the dialog agents in the task tree need to be brought into focusin light of the recently gathered information from user input 580. Forexample, dialog engine 550, or the task manager, may determine, byanalyzing the dialog input received from the user, whether the userdesires to initiate a different task or shift the focus of theconversation to perform a task subroutine (e.g., dialog agent and/ordialog agency) not immediately scheduled for execution following thetask subroutine currently being executed. Shifting focus of the tasksubroutine execution based on recently received user input may be aprocess similar to the construction of expectation agenda 570 in thateach of the dialog agents in task tree 500 may be given an opportunityto declare a focus claim. Focus claims may be domain dependent and maybe specified as trigger conditions of the dialog agents. If any dialogagent signals for a focus shift (i.e., submits a focus claim), theclaiming dialog agent may be pushed by dialog engine 550 onto dialogstack 560 for execution. For example, if the claiming dialog agentindicates that the focus shift to its particular subroutine is requiredaccording to user input 580, then the claiming dialog agent is pushed tothe top of the dialog stack.

In the event that there are no dialog agents claiming a focus shift,then dialog engine 550 may determine whether the dialog requires amodification of the task specification. The task manager or dialogengine 550 may be configured to allow modification of the taskspecification during runtime. For example, task tree 500 may be modifiedto add dialog agencies or dialog agents to preexisting dialog agencies,to remove preexisting dialog agencies or agents from task tree 500, orto change how preexisting dialog agencies and agents are ordered withrespect to each other in task tree 500. Dialog engine 550 may beconfigured to mirror such a change in the task specification to theorder of dialog agents in expectation agenda 570 and dialog stack 560.For example, when a user requests to reserve four different conferencerooms, task tree 500 may be modified to repeat one or more of dialogagencies 512, 514 and dialog agents 516, 530, 532, 534, 540, 542, and544 such that four different conference rooms are reserved based on thedifferent search criteria for each of these four different conferencerooms that the user has specified. Task manager or dialog engine 550 maymodify the task specification in such a way as to minimize the number ofturns in which information for all four instances of the conference roomreservation is prompted to the user. Queries for information requiredfor multiple instances of several task subroutines may be consolidatedto facilitate faster and more efficient execution of the task. Forexample, if the user desires to reserve four different conference rooms,the task manager may instruct the dialog engine 550 of the conferenceroom reservation task to repeat execution of the GetQuery dialog agency514, the GetResults dialog agency 512, the Discuss Results dialog agency516, the DateTime dialog agent 530, the Properties dialog agency 534,the Network dialog agent 540, the Projector dialog agent 542, and theWhiteboard dialog agent 544. The task manager may instruct dialog engine550 to repeat execution of these dialog agents and agencies for fourtimes in the order specified in task specification 500. The task managermay instruct the dialog engine 550 to repeat execution of these dialogagents and agencies for an additional three times once GetQuery dialogagency 514 receives dialog input from the user that requests reservationof four different conference rooms instead of the expected request ofone room. Accordingly, the dialog engine may be able to dynamicallyscale the task according to instructions received from the user dialoginput. The dialog engine 550 may communicate dialog input received fromany dialog agent and dialog agency to the task manager so that the taskmanager can appropriately instruct the dialog engine how to scale thetask and the order in which dialog agents and agencies are to be placedon dialog stack 560. However, the task manager may instruct the dialogengine to not repeat the Login dialog agency 510 and its subsumed dialogagents 520, 522, 524, and 526 more than once in order to avoid greetingthe user and requiring logging on multiple times. By repeating certaindialog agents and agencies and not others, the application may performthe task in a sophisticated manner.

Upon termination of the input phase for a particular dialog agentsand/or agencies, dialog engine 550 may initiate the execution phase ofthe next dialog agent or agency positioned at the top of dialog stack560. In this order, dialog engine 550 may continue to traverse down tasktree 500 and perform subroutines corresponding to the various dialogagents and agencies of task tree 500. Once dialog engine 550 hastraversed task tree 500 and reached the last of the dialog agents intask tree 500 and determines that there are no additional dialog agentsor agencies to be added for execution based on focus shifts, userinputs, or to improve conversational strategies, dialog engine maycomplete execution of the task. The task manager may retrieve usefulinformation in the form of stored user input values, dialog agent outputfor use in another task that may require such information that hasalready been acquired and processed by the currently executing task forefficient execution of future tasks. Dialog engine 550 may terminateexecution of the currently running task and signal the task manager thatthe currently running task has completed.

FIG. 6 depicts a task management system 600 comprising task manager 602in communication with multiple tasks of a dialog application. In someembodiments, task manager 602 may comprise several subcomponents, eachresponsible for performing a set of functions. As described by theembodiment shown in FIG. 6, task manager 602 may comprise task executionengine 610, task monitor 612, task object retriever 614, task scheduler616, task manipulator 618, and task selector 620. Each of thesesubcomponents may be performed either by a single processor differentprocessors or even different computing devices. In other embodiments,each of the functions performed by task manger 602 may not be groupedinto modular subcomponents as described in FIG. 6, but can be performedby a single processor executing task manager 602. Task manager 602 maybe in communication with dialog engines corresponding to the varioustasks that it manages such as dialog engines 630, 632, and 634. In someembodiments, task manager 602 may handle tasks for a particular dialogapplication and different task managers may handle tasks for otherdialog applications. These multiple task managers may communicate witheach other for cross application communication. In other embodiments,task manager 602 may manage tasks performed by multiple dialogapplications.

Tasks may be executed independently based on an intent basedinterpretation or they may be executed directly by a dialog applicationusing task manager 602. Under intent based execution, a dialogapplication may launch tasks automatically based on an NLU ranking ofuser commands, state of the dialog, application specific intentevaluation programs, and intent slots. For example, an NLUinterpretation of the user input may be used to determine which task tolaunch by identifying the intent of the dialog. However, when tasks areinvoked directly by the dialog application, the dialog application mayinvoke an instance of task manager 602 to create and execute its tasks.

In some embodiments, the task manager 602 may invoke and manageexecution of all tasks. The task manager may schedule task executionbased on a predefined order specified in the programming of the taskmanager 602. Task manager 602 may schedule execution of a plurality oftasks once a specific type of dialog input is received from the user orin response to another trigger. For example, if the user says “Arrange acatered dinner party with my coworkers for Thursday night,” task manager602 may schedule execution of a multiple tasks in a specific order. Taskmanager 602 may first schedule a home cleaning task in which the usercan specify parameters for scheduling a maid service appointment toclean the house. Second, the task manager 602 may schedule execution ofa dinner catering task in which the user can specify, as dialog input,parameters for what type and how much food is to be ordered. Third, thetask manager 602 may schedule execution of an invitation task in whichemail invitations can be sent to the user's coworkers and a partyinvitation can be created on a social media website. The user canspecify, as dialog input, the parameters of which coworkers to inviteand include additional details in the invitation task. Task manager 602may be able to schedule execution of these three tasks automatically byparsing the dialog input of a command such as “Arrange a catered dinnerparty with my coworkers for Thursday night.” Once a particular task isfinished, the task manager 602 may execute the next task scheduled forexecution. In scheduling these tasks for execution, the task manager 602may assign task identifiers to each scheduled task to manage executionof each task and pass values between different tasks.

Task manager 602 may be initiated to start a new session by a dialogapplication. Task manager 602 may determine which task to executeinitially and may also determine the order of execution of all othertasks managed by the dialog application. For example, when a new eventsession is processed, task manager 602 may initiate execution of aninitial task specified by the dialog application. The task instanceidentifier of such an initial task and all other tasks, which uniquelyidentify instances of a given task, may be associated with the task, bytask manager 602, until the task completes, exits or is aborted. Taskmanager 602 may also initialize tasks with dialog agent values byproviding a map of dialog agent identifiers (i.e., addressinginformation for dialog agents in a task specification) to such storedvalues to be inputted to a task's specific dialog agents.

Task manager 602 may be configured to create, suspend, resume, abort,and exit different tasks. For example, task execution engine 610 maycreate a task object for a task requested by dialog application andassign that task a task identifier for future addressing. The taskidentifier may be formatted to be compatible with other task identifiersused by tasks for different dialog application systems for anyinter-application task communication. Task execution engine 610 maybegin execution of the task by instructing the dialog enginecorresponding to the task to begin examining the task specification andinitiate the execution phase. If task manager 602 detects that anothertask is running, then task execution engine 610 may determine if thecurrently executing task can be suspended in favor of the newlyrequested task. If it is determined that such a suspension ispermissible, task execution engine 610 may suspend execution of thecurrently executing task (i.e., by invoking the suspend dialog agency tothe top of the dialog stack of the currently executing task) and startexecution of the newly requested task. Once the newly requested task hascompleted execution (i.e., task manager 602 may receive a message fromthe newly requested task signaling its completion), task executionengine 610 may resume running the previously executing task that wassuspended. Task execution engine 610 may recall all of the stored userinput values, parameters, and state of the previously running task andpass those values to the resumed task (i.e., task manager 602 may push aresume dialog agent, which is responsible for recalling such values, tothe top of the dialog stack of the resumed task). If there is anothertask running when a task is resumed in response to a user command, taskexecution engine 610 may suspend that task and resume the task requestedto be resumed. In response to user input command to abort a particulartask, task execution engine 610 may immediately abort execution of thattask without preserving state of the aborted task or generating anycallbacks to the aborted task. Task manager 602 may place the dialogapplication into an idle state if there are no other tasks scheduled forexecution.

Task manager 602 may also establish callback handlers for tasks that itmanages. For example, task execution engine 610 may comprise aninterrupt service handler subroutine that can be used to initiate newtasks, resume a previously running task, suspend a currently runningtask, abort a currently running task, or exit a completed task. Taskexecution engine 610 may execute such callback handlers once a triggeris set off. Such triggers may be set off in response to user commands toinitiate new tasks, resume, suspend, abort or exit tasks.

Task manager 602 may be configured to manage different tasks bymonitoring the state of different tasks. For example, task monitor 612,a subcomponent of task manager 602, may detect a state of any task thatthe dialog application desires to manage. For instance, whenever taskmanager 602 may check to see if any tasks are currently running ordetermine the last active time of any tasks, task monitor 612 may querythe state of such a task by implementing a task state monitor functioncall. Task monitor 612 may receive the task identifier from task manager602 and use such a task identifier to identify, task instance identifierand current state (i.e., one of created, active, suspended or finished)of a particular task. Task monitor 612 may be configured to return thedialog state of any task (i.e., the current state of execution of thetask specification). For example, task monitor 612 may determine whichdialog agent a currently running task is executing and whether thedialog engine is executing the input phase or the execution phase ofthat dialog agent by communicating with the dialog engine for thatcorresponding task. Task monitor 612 may also determine the state oftask manager 602. For example, task monitor 612 may determine if taskmanager 602 is currently busy executing a function call and may schedulefunction calls by the task manager.

In addition to retrieving parameters from tasks, task manager 602 mayalso retrieve task objects. For example, task object retriever 614 mayretrieve the task specification structure. For example, when taskmanager 602 decides to generate a new task tree for a newly requestedtask, task manager 602 may create a model for such a task using the taskspecification of one or more related tasks. Accordingly, task objectretriever 614 may retrieve the task tree of such one or more taskspecifications. Task object retriever 614 may also retrieve a parameteror stored value from a currently running or completed task. For example,task object retriever 614 may retrieve user input values from parseddialog, concepts, dialog agent outputs, data structures, and evensoftware subroutines from any given task, currently executing or onethat has completed execution. Task monitor 602 may retrieve such data inresponse to determining that another task may be able to use thisinformation for its own execution.

Task manager 602 may retrieve a list of task objects for all tasks. Forexample, task object retriever 614 may communicate with task monitor 612to determine the time each task was last active and accordingly mayobtain a list of task objects ordered according to the amount of timesince the task was last active. Task object retriever 614 may beconfigured to retrieve a task object for a particular task by supplyingthe task identifier. Task object retriever 614 may use the taskidentifier and retrieve the active task addressable using the taskidentifier. If the task requested is not an active task, then taskobject retriever 614 may retrieve a null object. Task object retriever614 may also be commanded to retrieve the task object of a currentlyrunning task.

Task manager 602 may be configured to schedule tasks for execution. Forexample, task scheduler 616 may identify tasks scheduled for executionbased on received user input. Task scheduler 616 may determine an orderof execution for the scheduled tasks by analyzing the dialog to identifyif the user has requested execution of a particular task before anyother tasks. The task schedule 616 may rely on its own application logicto determine an order of execution for each of its scheduled tasks basedon the preconditions, triggers, and completion criteria of each of thetasks. For instance, if task scheduler 616 determines that if a firsttask produces output that can be used to expedite the processing ofother tasks, then that first task may be scheduled before the othertasks. As another example, if task scheduler 616 determines that asecond task is requested by the user for execution by an urgentlyapproaching deadline or with some indication of urgency, then taskscheduler 616 may schedule the second task for execution earlier thanother tasks. Task scheduler 616 may determine the next task scheduledfor execution when a task is currently running and may even initializethe second task while the first task is running. The task scheduler 616may also receive instructions from a task selector 620 for any task thatit manages signaling if the order of execution of tasks needs to bemodified based on activities within the task or due to additionalinstructions received from the user while the given task is beingexecuted.

Task manager 602 may also set values for a currently running task or atask scheduled for execution. For example, task manipulator 618 may setvalues for concepts in the expectation agenda of particular dialog agentor agency. Task manager 602, using task object retriever 614, may havepreviously retrieved values for [user_name] from previous user logon fora separate task (i.e., online conference task associated with the sameapplication used to reserve conference rooms according to the exampledescribed above with relation to FIG. 5). Task manipulator 618 may setthe value for [user_name] in the currently running task to reserveconference rooms that it has retrieved from the online conference task.Task manipulator 618 may also directly set initial values for certaintasks while it is initializing such tasks. Task manipulator 618 may alsoset parameters for a given task. For example, task manipulator 618 maybe able to pass a basic type, list, or map to a task for its subsequentuse.

Task manager 602 may be configured to implement remote procedure calls(RPC) to enable distributed processing of task execution. For example,task manager 602 may initiate an inter-process communication techniquethat allows an application, which is executed partially on a user deviceand partially on a remote server in communication with the user devicethrough a networked connection, to execute the task in a remote serveraddress space without having to explicitly program the details of theremote interaction. For instance, task manager 602 may use common RPClibraries, security, synchronization, and data flow handling techniquesto allow such distributed task execution to allow asynchronous taskcontrol. As an example, task manager 602, running on the user device mayinitiate function calls to a remote server implementing the task, byissuing commands to the remote server using RPC methods to create,suspend, resume, abort, and exit particular tasks.

Task manager 602 may comprise a task selector 620 which can interpretvoice and text commands to control task execution. Task selector 620 mayallow task manager 602 to override a default next task in response to auser command. For example, task scheduler 616 may automatically set adefault next task for execution and a default initial task for executionwhen a dialog application starts. However, a user may specify that hewants a particular task to be run during execution of a currentlyrunning task. In this case, task selector 620 may initiate functioncalls to override the default next task set for execution by taskscheduler 616 and may instead identify and select the task specified bythe user command for execution. Task selector 620 may allow the dialogapplication to switch to a new task while a task is currently running inresponse to a user command. Task selector 620 may preserve the currentlyrunning task information and work with task execution engine 610 toestablish callback handler routines to suspend and later resume thecurrently executing task and then to create and execute the taskidentified by task selector 620 in response to the user command.

In some embodiments, the task selector 620 may be a distributedcomponent that runs on both task manager 602 and in different taskdialog engines 630, 632, and 634. For example, task selector 620 may bea part of the dialog engines of different tasks which allows the dialogengine the ability to decide when to suspend their own task in favor ofanother task and/or the ability to modify the task that they areresponsible for. Task selector 620 may be comprised of instructions inan application definition file that controls how a particular task cancommunicate between a dialog engine and the task manager to implementthe task selector commands (e.g., the portion of task selector 620executing on task manager 602). Task selector 620 may also be comprisedof task specific instructions encoded by each task managed by the taskmanager (e.g., the portion of the task selector 620 executing on thetask dialog engines). The task specific instructions for each task maydefine how the dialog engine is to modify execution, suspend, and resumethe task's dialog agents and agencies in response to certain userinstructions. The dialog engine may be configured to launch bothapplication definition file instructions and task specific instructionsto generate an application decision layer (e.g., the task selector)which selects what task to launch based on the dynamic dialog inputreceived from the user. The task selector may continuously monitor alldialog input instructions received from the user and accordinglyinstruct the dialog engine which dialog agent and/or agency to push ontothe top of the dialog stack in response to the received dialog input.The task selector may also instruct the dialog engine to communicatewith the task manager to communicate that the current task needs to besuspended and a new task needs to be launched based on the receiveddialog input. For example, if the user specifies that he wishes to ordera large pizza, the task selector may determine that a promotional taskis to be launched to offer the user a free drink if the user answers asurvey. The task selector may comprise instructions specifying that thepromotional task is to be launched only if the user orders a large sizedpizza instead of a small or medium sized pizza.

In some embodiments, task manager 602 may be configured to allowmultiple tasks to use the same task specification. For example, taskmanager 602 may expand each task's task definition such that each taskdefinition has a “name” property which allows multiple tasks to use thesame task tree structure but to have different initial values and taskhandlers. The initial values element may allow task manager 602 tospecify dialog agent values to be set as a task is being created. Taskmanger 602 may use a “class” property associated with a task to allowthe dialog application to receive callbacks to start, exit, suspend, orresume a task by specifying the “class” property. Task manger 602 mayuse a “selection mode” property associated with a task to allow thedialog application to control when a task may be selected by taskselector 620. Values of the “selection mode” property may either allowtask selector 620 to control a task either always, when the task is notactive, when the task does not exist, or never. For example, certaintasks may be configured such that the task selector 620 may not modifytheir operation. Other tasks may allow task selector 620 to suspend ormodify the order of their execution whenever the task selector 620 bestdetermines to be fit. Other tasks may allow the task selector 620 tomodify the order of execution of tasks or suspend the task in favor of adifferent task only if certain criteria are met. The “selection mode”property in each task may specify such preferences and any suchselection criteria that govern the conditional access given to taskselector 620 to modify the execution of the task.

In some embodiments, task manager 602 may be able to rerank semanticinterpretations of the dialog between the dialog application system andthe user by continuously monitoring dialogs. For example, the taskmanager 602 may monitor dialogs across each of its tasks, both past andpresent, and rerank interpretations for specific types of dialogs basedon such monitoring. Task manager 602 may apply the best rankedinterpretation to received user input involving similar types ofdialogs. Each time a dialog application NLU engine such as NLU engine203 of FIG. 2 determines a semantic interpretation from parsed userinput in the dialog with the dialog application system, the NLU enginemay rerank all of the schematic interpretations to include the currentlyranked semantic interpretation.

Task manager 602 may either launch a new task by applying a functioncall for the next scheduled task expecting an input or task manager 602may apply the best available semantic interpretation for the entereduser input in order to best determine which task the user input mostappropriately calls for. For example, when a new user input is entered,the dialog application system may determine what type of input the newlyentered user input can be classified as and may assign a best fit taskto that user input using the best ranked semantic interpretation. Byapplying the best semantic interpretation, the dialog application system600 may best be able to understand the true goal and intent of the usercommand and accordingly may launch tasks to achieve that goal. Taskmanager 602 may add, remove, or modify intent slots in the best semanticinterpretation to associate the semantic interpretation of a usercommand to a particular task. Task manager 602 may process a user inputand determine that such a user input was best semantically processedwhen a particular type of task was executed. The next time such a userinput type is encountered, task manager 602 may add an intent slot tothe parsed user input and may apply the semantically best fit task tothat parsed user input command as identified by the intent slot found inthe best fit semantic interpretation. In such situations, the user maynever be exposed to semantic interpretations. Instead, the user merelysees that a particular task is executed once his user input is enteredinto the dialog application system. Alternatively, if there are nosemantic interpretations that fit the user input, then task manager 602may not execute any tasks based on the user input.

FIG. 7 depicts an illustrative method 700 for coordinating execution ofmultiple dialog tasks in accordance with one or more exampleembodiments. In one or more embodiments, method 700 of FIG. 7 and/or oneor more steps thereof may be performed by a dialog application runningon a computing device (e.g., client computing devices 107 and 109 ordata server 103). In other embodiments, method 700 illustrated in FIG. 7and/or one or more steps thereof may be embodied in computer-executableinstructions (i.e., the dialog application) that are stored in acomputer-readable medium, such as a non-transitory computer-readablememory. The term “dialog application system,” as used hereinafter withrelation to FIG. 7 may refer to either client computing devices, remoteserver, computer readable medium, or any combination of one or moredevices with processing circuitry used to perform one or more steps ofmethod 700.

As seen in FIG. 7, the method may begin at step 702 in which the dialogapplication system may receive user commands. The user commands may beinput as either text or speech input into a client computing device suchas user client 201 of FIG. 2. Speech and text user commands may beprocessed by an ASR engine, NLU engine, and a context sharing modulebefore being processed by a dialog application system into parsed usercommands. A task manager associated with the dialog application system,such as task manager 302 of FIG. 3 and task manager 602 of FIG. 6, mayprocess the parsed commands.

In step 704, the dialog application system may apply a best rankedsemantic interpretation to the received user commands. The dialogapplication system may process the parsed user input for implementingtasks by first understanding the intent of the user command.Accordingly, the dialog application system's task manager may identifywhich class of previously categorized class order of user inputs thereceived user input best matches. Upon identifying the class of userinput, the task manager may apply the best semantic interpretation forthat particular class of user input to the received user input.

In step 706, the dialog application system may identify one more tasksfor execution. By applying the best ranked semantic interpretation tothe received user input, the task manager may identify the intent of theuser command and may identify one or more tasks for execution. Suchidentified tasks may be associated with the best ranked semanticinterpretations applied to the user commands. The task manager mayschedule the identified tasks according to an appropriate order bydetermining the urgency of the user requested tasks. Task manager mayalso identify an initial task for execution at the time of applicationlaunch, the execution of which may be performed independently ofreceiving any user commands.

In step 708, the dialog application system may initiate execution of theone or more identified tasks. The dialog application system's taskmanager may initiate a function call or a remote procedure call toexecute a task identified for imminent execution. Task manager may passavailable values and parameters to a dialog engine of the correspondingtask in the function call. The task dialog engine may identify dialogagents and/or agencies from the dialog task's corresponding taskspecification and order execution of such dialog agents and/or agenciesin a dialog stack. The dialog engine may alternate between an executephase and an input phase for each dialog agent and/or agency as ittraverses down a task tree of the task specification. The dialog enginemay construct an expectation agenda for each dialog agent and/or agencyand may facilitate a dialog with the user. The dialog engine may processthe parsed user inputs to perform functions that fulfill the completioncriteria of the task.

In step 710, the dialog application system may monitor user speech inputduring execution of an identified task. The dialog engine and taskmanager of the dialog application system may each monitor the speechinput received during execution of a task in order to facilitateexecution of the task and also to determine if the user wants to performactivities related to other tasks. For example, the task manager maymonitor a processed user input to determine if the user desires tocreate a new task, suspend, abort or exit the current task, or resume apreviously suspended task. User commands for performing such taskrelated functions may be received asynchronously and the task managermay also facilitate asynchronous control over its managed tasks.

In step 712, the dialog application system may determine whetherexecution of a new task has been requested before the current task hascompleted. For example, the task manager may determine whether a task isrequested for execution at a time during which a currently active taskis executing. The dialog application system may determine the urgency ofthe requested task and determine whether its execution can be delayed toa later time when the currently active task has completed its execution.The task manager may further determine whether execution of the newlyrequested task is critical for completion of the currently active task.

In response to determining that the execution of a new task has beenrequested before the current task has completed, in step 714, the dialogapplication system may suspend execution of the currently active task.If the task manager determines, as a result of performing suchdeterminations described in step 712, that the newly requested must beexecuted before the currently active task has completed execution, thenthe task manager may suspend execution of the currently active task. Forexample, the task manager may initiate a callback routine handler toinvoke the currently active task's dialog engine to place a suspenddialog agency at the top of its dialog stack. Accordingly, the dialogengine of the currently active task, under direction of the taskmanager, may preserve the current state of execution of the task, storeany user input values, initialized task subroutines, generatedexpectation agendas, dialog stacks, and parsed user input to be laterrecalled when the task is resumed. The dialog engine of the current taskmay signal the task manager when the task has been suspended.

In step 716, the dialog application system may retrieve parameter valuesfrom user input and previously active tasks. The task manager mayretrieve any information such as user input values and any otherparameters obtained from previously active tasks that may be necessaryfor the execution of the newly requested task. The task manager may beable to identify the parameters that the newly requested task requiresby examining the inputs required by the newly requested task's dialogagents and agencies. The task manager may retrieve such values fromvarious tasks that it identifies may have already received and storedsuch data as a virtue of their previous implementation. Accordingly, thetask manager may retrieve such data from storage locations in whichvarious previously active tasks have preserved parsed user input andsuch data.

In step 718, the dialog application system may transmit the retrievedparameter values to a newly requested task. For example, the taskmanager may transmit, to the newly requested task, the data required bythe newly requested task that the task manager has retrieved from anypreviously active tasks and user input. Upon transmitting such data tothe newly requested application, method 700 may return to step 708 wherethe dialog application system may again initiate execution of theidentified task. For example, the task manager may execute the newlyrequested task by performing steps 708, 710, 712, 714, 716, and 718again in a loop. Such a loop may continue until a currently active taskis not suspended because of another new task being requested before thecurrently active task reaches successful completion.

In step 720, the dialog application system may determine whether thecurrently active task has completed execution. If the task manager hasnot suspended the currently active task and determined, in step 712,that the execution of a new task has not been requested before thecurrent task has completed, then task manager 720 may determine whetherthe currently active task has completed its execution. The task managermay periodically perform step 720 during execution of the currentlyactive task. Alternatively, the task manager may only perform such adetermination once it has determined that the completion criteria of allof the dialog agents and agencies of the currently active task have beenmet.

In step 722, the dialog application system may identify the next task tobe executed in response to determining that the currently active taskhas completed execution. Once the task manager has determined in step720 that execution of the currently active task has completed, the taskmanager may identify the next task to be executed. For example, the taskmanger may determine from a schedule of tasks which task is to beexecuted next by examining user dialog input. Upon identifying the nexttask for execution, method 700 may return to step 708 where the dialogapplication system may again initiate execution of the identified task.For example, the task manager may execute the next scheduled task byperforming steps 708, 710, 712, 714, 716, and 718, 720, and 722 again ina loop. Such a loop may continue until there are no tasks scheduled forexecution, in which case method 800 may optionally return to step 702and wait for further user commands instructing the dialog application toexecute new tasks.

FIGS. 8A and 8B depict an illustrative method 800 by which a dialog taskmay be executed in accordance with one or more example embodiments. Inone or more embodiments, method 800 of FIGS. 8A & 8B and/or one or moresteps thereof may be performed by a task's dialog engine such as dialogengine 550 of FIG. 5B. Method 800 of FIGS. 8A & 8B may describe theprocesses implemented in step 708 of FIG. 7. In other embodiments,method 800 and/or one or more steps thereof may be embodied incomputer-executable instructions (i.e., the dialog application) that arestored in a computer-readable medium, such as a non-transitorycomputer-readable memory.

As seen in FIG. 8A, method 800 may begin at step 802 in which the task'sdialog engine may determine the order of execution of dialog agentsand/or agencies in the task's dialog stack. The task dialog engine mayexamine the task's specification to determine the relationship of thevarious dialog agents and dialog agencies with relation to each other asidentified by a task tree in the task specification. The dialog enginemay examine the task tree and accordingly schedule the various dialogagents and/or agencies for execution in the order specified in the taskspecification. For example, the dialog engine may traverse down thedialog task tree and place the lowermost dialog agent on the task treeon the top of a dialog stack. Dialog engine may also place dialog agentsand agencies found at higher up nodes in the task tree lower on thedialog stack than dialog agents that are subsumed by them. Such orderingof the dialog stack may provide an order of execution to the variousdialog agents and/or agencies identified by the task's specification.

In step 804, the dialog engine may execute a dialog agent or agencypositioned at the top of the dialog stack. Once the dialog stack hasbeen assembled, the dialog engine may execute the dialog agent or agencylocated at the top of the dialog stack. The dialog engine may alwaysonly execute the dialog agent or agency that is located at the top ofthe dialog stack. Upon completion of such a dialog agent or agency, thedialog engine may remove that completed dialog agent or agency from thetop of the dialog stack such that the dialog agent or agency locatedbelow the previously active dialog agent or agency on the dialog stackrises to the top of the dialog stack. In this manner, the dialog enginemay execute all the dialog agents and agencies in the order in which thedialog stack specifies by executing the dialog agent or agency thathappens to be located at the top of the dialog stack. The dialog enginemay first initiate the execution phase of the dialog agent or agency tobe later followed by the input phase. In the execution phase, the dialogengine may perform functions specified by the dialog agent. For example,the dialog engine may display information to the user, requestinformation from the user, perform backend processes, implementconversational strategies, monitor NLU performance of other dialogagents and/or agencies etc.

In step 806, the dialog engine may determine whether the dialog agent oragency requests information from the user. For example, the dialogengine may determine whether the dialog agent or agency currently beingexecuted is a request type dialog agent or agency. The dialog engine maydetermine the type of the dialog agent or agency by examining theparameters of the dialog agent or agency specified in the taskspecification. If the dialog engine determines that the dialog agent oragency requests information from the user, the dialog engine mayinitiate the input phase by proceeding to step 812.

In step 808, the dialog engine may determine whether execution of thedialog agent or agency has completed. If the dialog agent or agencycurrently being executed by the dialog engine is not a request typedialog agent, the dialog engine may complete its execution phase whenall of its function calls have been executed. Accordingly, the dialogengine may determine whether the dialog agent or agency has indicatedthat that its execution phase has terminated (i.e., by triggering itsinput phase).

In response to determining that the execution of the dialog agent oragency has completed, in step 810, the dialog engine may remove thedialog agent or agency from the top of the execution stack. The dialogengine may remove dialog agents or agencies that have just completedtheir execution phase from the top of the dialog stack. The dialogengine may completely remove the dialog agent or agency from the dialogstack altogether or may position the dialog agent or agency at adifferent location in the dialog stack by examining whether the dialogagent or agency will be required to be executed again according to thedialog task's specification.

In step 812, the dialog engine may generate a portion of the expectationagenda corresponding to the dialog agent or agency. The dialog enginemay query the dialog agent or agency for data that it expects to receivefrom user input to construct sections of the expectation agenda relatedto the task. The expectation agenda may include concepts and parametersthat need to be initialized with user supplied information. Theexpectation agenda may be constructed piecemeal as the dialog enginesteps through the dialog agents and agencies according to the orderspecified in the dialog stack. The sections of the expectation agendathat are generated may list the parameters that are expected to beidentified and be associated with values during execution of thecorresponding dialog agent or agency.

In step 814, the dialog engine may receive user input from the user. Forexample, request and expect type dialog agents may receive direct userinput during their input phase. The dialog application may prompt theuser to enter information in a conversational dialog. Such prompting maybe executed during the execution phase of the dialog agent or agency.During the input phase, the dialog engine may capture the user's enteredspeech or text inputs to such prompts. Even if no prompts are requested(i.e., in the case of expect dialog agents), the dialog engine mayexpect to receive user input to aid in the execution of the task.Accordingly, the dialog engine may reserve a period of time during whichit awaits user inputs to be entered for such dialog agents and/oragencies. The dialog engine may receive parsed user inputs from the ASRengine.

In step 816, the dialog engine may associate user input values withconcepts in the expectation agenda. The dialog engine may analyze parsedreceived user inputs to identify which concepts identified in the dialogagent or agency's expectation agenda may be bound to the user inputtedvalues. Upon associating such user input values with the identifiedconcepts and subroutines awaiting user input values for initialization,the dialog engine may pass the values onto different dialog agent oragency in the task that may use such information to perform theirexecution phase.

In step 818, the dialog engine may determine whether the previouslyreceived user input requires a shift in the dialog focus. The dialogengine may analyze user input to determine whether there are anysemantic clues to indicate that a different dialog agent or agency needsto be implemented. For example, the dialog engine may determine that theuser has changed the focus of the conversation from supplying roomreservation information to specifying a list of attendees to invite tothe conference room according to the conference room reservation taskexample of FIG. 5.

In response to determining that the user input requires a shift in thedialog focus, in step 820, the dialog engine may identify a dialog agentor agency to position to the top of the dialog stack. In response todetermining that the focus of the conversation has shifted to a dialogagent or agency that is not immediately associated with the currentlyactive dialog agent or agency, the dialog engine may determine whichdialog agents and/or agencies to execute to address the focus shift inthe user dialog. The dialog engine may apply semantic interpretations tothe received user input dialog to determine which dialog agent or agencybest fits the semantic interpretation of the user input.

In step 822, the dialog engine may position the identified dialog agentor agency at the top of the dialog stack. Once the dialog engine hasidentified at least one dialog agent or agency to execute in response tothe focus shift, the dialog engine may position that identified onto thetop of the dialog stack for immediate execution. The dialog engine maydetermine that the particular dialog agent or agency is located lower inthe dialog stack and may retrieve it to place at the top of the stack.Once the dialog engine places the identified dialog agent or agency atthe top of dialog stack, method 800 may return to step 804 where thedialog engine may again execute the dialog agent or agency positioned atthe top of the dialog stack. The dialog engine may execute the newlypositioned dialog agent or agency by performing steps 804, 806, 808,810, 812, 814, 816, 818, 820, and 822 again in a loop. Such a loop maycontinue until no further focus shifts are required in step 818.

As depicted in FIG. 8B, in response to determining in step 818 that theuser input does not signal a shift in the dialog focus, in step 824, thedialog engine may determine whether the dialog requires modification ofthe task structure. For example, the dialog engine may monitor the userinput to determine whether the user commands require adding or removingdialog agents and/or agencies to the task tree of the currentlyexecuting task in order to better facilitate execution of the currenttask. For example, the dialog engine may determine that a particulartask requires modifying the task structure by replicating particulardialog agents or executing multiple instances of one or more dialogagents or agencies.

In response to determining in step 824 that the dialog requiresmodification of the task structure, in step 826, the dialog engine maymodify the task structure by adding or removing dialog agents and/oragencies to the dialog stack. For example, the dialog engine or the taskmanager may create new dialog agents and/or agencies or new instances ofpreexisting dialog agents and/or agencies in the dialog stack.Alternatively, the dialog engine or the task manager may removepreexisting dialog agents and/or agencies from the dialog stack. Suchmodification of the dialog stack may be reflected in the expectationagenda and may help customize the dialog to meet the needs of the user.The task specification of any given task may be a scalable such thatdialog engine may add or remove dialog agents and/or agencies to thetask's tree structure in runtime to adapt to the dialog. Once the dialogengine modifies the task structure by modifying the task's dialog stackand expectation agendas, method 800 may return to step 804 where thedialog engine may again execute the dialog agent or agency positioned atthe top of the dialog stack. The dialog engine may execute the newlypositioned dialog agent or agency by performing steps 804, 806, 808,810, 812, 814, 816, 818, 820, 822, 824, and 826 again in a loop. Such aloop may continue until no further focus shifts are required in step 818and no task structure modifications are required in step 824.

In response to determining in step 824 that the dialog does not requiremodification of the task structure, in step 828, the dialog engine maydetermine any dialog agents or agencies are left on the dialog stackawaiting execution. The dialog engine may monitor the dialog stack todetermine whether any dialog agents or agencies of a given task have notbeen executed. If it is determined that there are indeed dialog agentsand/or agencies awaiting execution on the dialog stack, the method mayproceed to step 804 to execute the dialog agent or agency positioned atthe top of the dialog stack. The dialog engine may complete its inputphase when it has determined that all dialog agents and/or agenciesidentified in the task tree (and the dialog stack) have been executedand have met their respective completion criteria.

In response to determining that there are no dialog agents or agenciesawaiting execution on the dialog stack and that completion criteria forall of the dialog agents and/or agencies have been met, in step 830, thedialog engine may transmit parameters from the task's dialog agentsand/or agencies to the task manager. For example, the dialog engine mayretrieve any information such as user input values and any otherparameters obtained from its dialog agents and/or agencies that may beuseful for the execution of other tasks that may share the same dialogagents and/or agencies. The task manager may request such informationfrom the dialog engine once it detects that the task is nearingcompletion and has such information to supply.

In step 832, the dialog application system may terminate the task. Forexample, the dialog engine may transmit a message to the task managerindicating that it has met its completion criteria and accordingly isready to be terminated. Accordingly, the task manager may invoke an exitcallback handler subroutine. The exit callback handler subroutine mayterminate the task and clear any active task state from the memory ofthe computing device upon having preserved the necessary informationthat the task manager needs to store from the task.

Although the subject matter has been described in language specific tostructural features and/or methodological acts, it is to be understoodthat the subject matter defined in the appended claims is notnecessarily limited to the specific features or acts described above.Rather, the specific features and acts described above are disclosed asexample forms of implementing the claims.

One or more embodiments may be implemented in any conventional computerprogramming language. For example, embodiments may be implemented in aprocedural programming language (e.g., “C”) or an object-orientedprogramming language (e.g., “C++”, Python). Some embodiments may beimplemented as pre-programmed hardware elements, other relatedcomponents, or as a combination of hardware and software components.

Embodiments can be implemented as a computer program product for usewith a computer system. Such implementations may include a series ofcomputer instructions fixed either on a tangible medium, such as acomputer readable medium (e.g., a diskette, CD-ROM, ROM, or fixed disk)or transmittable to a computer system, via a modem or other interfacedevice, such as a communications adapter connected to a network over amedium. The medium may be either a tangible medium (e.g., optical oranalog communications lines) or a medium implemented with wirelesstechniques (e.g., microwave, infrared or other transmission techniques).The series of computer instructions may embody all or part of thefunctionality previously described herein with respect to the system.Such computer instructions may be written in a number of programminglanguages for use with one or more computer architectures or operatingsystems. Furthermore, such instructions may be stored in any memorydevice, such as semiconductor, magnetic, optical, or other memorydevices, and may be transmitted using any communications technology,such as optical, infrared, microwave, or other transmissiontechnologies. Such a computer program product may be distributed as aremovable medium with accompanying printed or electronic documentation(e.g., shrink wrapped software), preloaded with a computer system (e.g.,on system ROM or fixed disk), or distributed from a server or electronicbulletin board over a network (e.g., the Internet or World Wide Web).Some embodiments may be implemented as a combination of both software(e.g., a computer program product) and hardware. Still other embodimentsmay be implemented as entirely hardware, or entirely software (e.g., acomputer program product).

A described “process” is the performance of a described function in acomputer using computer hardware (such as a processor,domain-programmable gate array, or other electronic combinatorial logic,or similar device), which may be operating under control of software orfirmware or a combination of any of these or operating outside controlof any of the foregoing. All or part of the described function may beperformed by active or passive electronic components, such astransistors or resistors. Use of the term “process” does not necessarilyimply a schedulable entity, although, in some embodiments, a process maybe implemented by such a schedulable entity. Furthermore, unless thecontext otherwise requires, a “process” may be implemented using morethan one processor or more than one (single- or multi-processor)computer and it may be an instance of a computer program or an instanceof a subset of the instructions of a computer program.

One or more aspects of the disclosure may be embodied in computer-usabledata or computer-executable instructions, such as in one or more programmodules, executed by one or more computers or other devices to performthe operations described herein. Generally, program modules includeroutines, programs, objects, components, data structures, and the likethat perform particular tasks or implement particular abstract datatypes when executed by one or more processors in a computer or otherdata processing device. The computer-executable instructions may bestored on a computer-readable medium such as a hard disk, optical disk,removable storage media, solid-state memory, RAM, and the like. Thefunctionality of the program modules may be combined or distributed asdesired in various embodiments. In addition, the functionality may beembodied in whole or in part in firmware or hardware equivalents, suchas integrated circuits, application-specific integrated circuits(ASICs), field programmable gate arrays (FPGA), and the like. Particulardata structures may be used to more effectively implement one or moreaspects of the disclosure, and such data structures are contemplated tobe within the scope of computer executable instructions andcomputer-usable data described herein.

Various aspects described herein may be embodied as a method, anapparatus, or as one or more computer-readable media storingcomputer-executable instructions. Accordingly, those aspects may takethe form of an entirely hardware embodiment, an entirely softwareembodiment, an entirely firmware embodiment, or an embodiment combiningsoftware, hardware, and firmware aspects in any combination. Inaddition, various signals representing data or events as describedherein may be transferred between a source and a destination in the formof light or electromagnetic waves traveling through signal-conductingmedia such as metal wires, optical fibers, or wireless transmissionmedia (e.g., air or space). In general, the one or morecomputer-readable media may comprise one or more non-transitorycomputer-readable media.

As described herein, the various methods and acts may be operativeacross one or more computing devices and one or more networks. Thefunctionality may be distributed in any manner, or may be located in asingle computing device (e.g., a server, a client computer, or thelike).

Aspects of the disclosure have been described in terms of illustrativeembodiments thereof. Numerous other embodiments, modifications, andvariations within the scope and spirit of the appended claims will occurto persons of ordinary skill in the art from a review of thisdisclosure. For example, one or more of the steps depicted in theillustrative figures may be performed in other than the recited order,and one or more depicted steps may be optional in accordance withaspects of the disclosure.

What is claimed is:
 1. A method comprising: identifying, by a computingdevice, that a first natural language user input, received at thecomputing device, comprises a request to perform a first dialog task;responsive to identifying a request to perform a first dialog task,initiating execution, by the computing device, of a first plurality oftask agents comprised by the first dialog task according to a firsthierarchical order by which task agents in the first plurality of taskagents are arranged for execution; responsive to a determination that asecond natural language user input, received at the computing deviceduring execution of the first dialog task, comprises a request toperform a second dialog task, determining, by the computing device, thatthe second dialog task is to be executed before execution of the firstdialog task is completed; and initiating execution, by the computingdevice prior to completion of the first dialog task, of a secondplurality of task agents comprised by the second dialog task in an orderbased on a second hierarchical order by which task agents in the secondplurality of task agents are scheduled for execution.
 2. The method ofclaim 1, further comprising: responsive to the second natural languageuser input requesting execution of a second dialog task, suspendingexecution, by the computing device, of the first dialog task; andpreserving, by the computing device, a state of a natural languagedialog and user inputs received during execution of the first dialogtask.
 3. The method of claim 2, further comprising: responsive todetermining that execution of the second dialog task has completed:retrieving, by the computing device, the state of the natural languagedialog and user inputs received during execution of the first dialogtask; and resuming execution, by the computing device, of the firstdialog task from a point at which the first dialog task was suspended.4. The method of claim 1, wherein execution of at least one task agentof the first plurality of task agents engages a user in a naturallanguage dialog to extract information, from the second natural languageuser input received during execution of the first dialog task, requiredfor the execution of the first dialog task.
 5. The method of claim 1,wherein initiating execution of the first plurality of task agentsfurther comprises scheduling for execution, by the computing device,each task agent of the first plurality of task agents in an order basedon the first hierarchical order of arrangement of the first plurality oftask agents, and wherein initiating execution of the second plurality oftask agents further comprises scheduling for execution, by the computingdevice, each task agent of the second plurality of task agents in anorder based on the second hierarchical order of arrangement of thesecond plurality of task agents.
 6. The method of claim 1, furthercomprising: responsive to receiving the request to perform a seconddialog task, determining, by the computing device, whether execution ofthe second dialog task should be prevented.
 7. The method of claim 1,further comprising identifying, by the computing device, which dialogtask is to be executed based on at least one of the second naturallanguage user input and information in the first plurality of taskagents.
 8. The method of claim 1, wherein the first dialog task and thesecond dialog task are managed simultaneously, the method furthercomprising: switching, by the computing, between different dialog tasksbased on a natural language dialog between the user and the computingdevice.
 9. The method of claim 1, wherein execution of the first dialogtask further comprises: generating, by the computing device, a list ofparameters that each of the first plurality of task agents expects toidentify from the natural language dialog; responsive to parsing thenatural language dialog, associating, by the computing device, at leastone user input value from the natural language dialog with eachparameter in the list of parameters; and executing, by the computingdevice, the first plurality of task agents using the at least one userinput value.
 10. The method of claim 1, further comprising: determining,by the computing device, that the second natural language user inputcomprises instructions to modify the first dialog task, currently beingexecuted, by adding additional task agents to the first hierarchicalorder; and scheduling for execution, by the computing device, theadditional task agents to the first dialog task currently being executedaccording to the first hierarchical order.
 11. An apparatus, comprising:at least one processor; and at least one memory storingcomputer-readable instructions that, when executed by the at least oneprocessor, cause the apparatus to: identify that a first naturallanguage user input, received at the computing device, comprises arequest to perform a first dialog task; initiate execution of a firstplurality of task agents comprised by the first dialog task according toa first hierarchical order by which task agents in the first pluralityof task agents are arranged for execution; responsive to a determinationthat a second natural language user input, received during execution ofthe first dialog task, comprises a request to perform a second dialogtask, determine that the second dialog task is to be executed beforeexecution of the first dialog task is completed; and initiate execution,prior to completion of the first dialog task, of a second plurality oftask agents comprised by the second dialog task in an order based on asecond hierarchical order by which task agents in the second pluralityof task agents are scheduled for execution.
 12. The apparatus of claim11, wherein the instructions, when executed by the at least oneprocessor, cause the apparatus to: suspend execution of the first dialogtask in response to the second natural language user input requestingexecution of a second dialog task; and preserve a state of a naturallanguage dialog and user inputs received during execution of the firstdialog task.
 13. The apparatus of claim 12, wherein the instructions,when executed by the at least one processor, cause the apparatus to:retrieve the state of the natural language dialog and user inputsreceived during execution of the first dialog task; and resume executionof the first dialog task from a point at which the first dialog task wassuspended.
 14. The apparatus of claim 11, wherein execution of at leastone task agent of the first plurality of task agents engages a user in anatural language dialog to extract information, from the second naturallanguage user input received during execution of the first dialog task,required for the execution of the first dialog task.
 15. The apparatusof claim 11, wherein initiating execution of the first plurality ofsubtasks further causes the apparatus to schedule execution of each taskagent of the first plurality of task agents in an order based on thefirst hierarchical order of arrangement of the first plurality of taskagents, and wherein initiating execution of the second plurality of taskagents further causes the apparatus to schedule execution of each taskagent of the second plurality of task agents in an order based on thesecond hierarchical order of arrangement of the second plurality of taskagents.
 16. The apparatus of claim 11, wherein the instructions, whenexecuted by the at least one processor, cause the apparatus to determinewhether execution of the second dialog task should be prevented.
 17. Theapparatus of claim 11, wherein the instructions, when executed by the atleast one processor, cause the apparatus to identify which dialog taskis to be executed based on at least one of the second natural languageuser input and information in the first plurality of task agents. 18.The apparatus of claim 11, wherein the first dialog task and the seconddialog task are managed simultaneously, and wherein the instructions,when executed by the at least one processor, cause the apparatus toswitch between different dialog tasks based on a natural language dialogbetween the user and the apparatus.
 19. The apparatus of claim 18,wherein the instructions, when executed by the at least one processor,cause the apparatus to: generate a list of parameters that each of thefirst plurality of task agents expects to identify from a naturallanguage dialog user input received at the apparatus; associate at leastone user input value from the natural language dialog user input witheach parameter in the list of parameters upon parsing the naturallanguage dialog user input; and execute the first plurality of taskagents using the at least one user input value.
 20. The apparatus ofclaim 11, wherein the instructions, when executed by the at least oneprocessor, cause the apparatus to: determine that a natural languagedialog user input, received at the apparatus, comprises instructions tomodify the first dialog task, currently being executed, by addingadditional task agents to the first hierarchical order; and schedule,for execution, the additional task agents to the first dialog taskcurrently being executed according to the first hierarchical order.